(chore) Address unreachable service check assertions in cloud_foundry_api oauth error tests#24282
Open
mwdd146980 wants to merge 1 commit into
Open
Conversation
…rror tests Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Contributor
Validation ReportAll 21 validations passed. Show details
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Restructures
test_get_oauth_token_errorsincloud_foundry_apiso itsaggregator.assert_service_check(...)calls actually execute.Motivation
Each error block wrapped both the raising call and the assertions after it in the same
pytest.raises(...)context:check.get_oauth_token()raises before reaching the lines after it, sopytest.raisescatches the exception and exits thewithblock immediately, which means that the assertion and reset are dead code. The fix nestspytest.raisesaround only the raising call, so the assertions run after the exception is caught, onceget_oauth_tokenhas already emitted its CRITICAL service check.This is a pre-existing test bug, called out separately from the W1b cloud_foundry_api catch-widening plan as explicitly out of scope there. It's unrelated to the httpx migration, so this PR targets
masterdirectly.Verification
OK(a value production never emits on this path) and confirmed the test still passed.OK-swap mutation against the fixed test and confirmed it now correctly fails, then reverted to the correctCRITICALassertion.ddev --no-interactive test cloud_foundry_api: all 23 tests pass.ddev test -fs cloud_foundry_api: formatting and lint clean.Review checklist (to be filled by reviewers)
qa/requiredif this PR needs QA validation, orqa/skip-qaif it does not. Exactly one of the two is required.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged